log backup: reset store grpc connection when encounter error (#50539) #50703
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
13 tasks
ti-chi-bot
added
ok-to-test
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release-7.1 #50703 +/- ##
================================================
Coverage ? 73.8442%
================================================
Files ? 1209
Lines ? 382183
Branches ? 0
================================================
Hits ? 282220
Misses ? 82219
Partials ? 17744 |
ti-chi-bot
added
the
cherry-pick-approved
BornChanger
approved these changes
Feb 23, 2024
YuJuncen
approved these changes
Feb 26, 2024
ti-chi-bot
bot
added
lgtm
and removed
needs-1-more-lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BornChanger, YuJuncen The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automated cherry-pick of #50539
What problem does this PR solve?
Issue Number: close #50445
Problem Summary:
advancer will cache the store grpc connection at first time connect to TiKV. This usually works well when TiKV normal scale-out/in or deploy with a domain name. but in some cases. when deploy TiKV cluster with IP address and IP changed.
the cached grpc connection will broken.
What changed and how does it work?
Disable the cached grpc connection when encounter error.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.